Managers frequently face ill-structured or "wicked" problems. Such problems are characterized by a large degree of uncertainty with respect to how the problem should be approached and how to establish and evaluate the set of alternative solutions. A design theory nexus is a set of constructs and methods that enable the construction of models that connect numerous design theories with alternative solutions. It thereby offers a unique problem-solving approach that is particularly useful for addressing ill-structured or wicked problems. For each alternative solution in a design theory nexus one or more unique criteria are established to formulate a specific design theory. We develop a general method for constructing a design theory nexus and illustrate its utility using two field studies. One develops and applies an organizational change nexus. The other develops and applies a user involvement nexus. Each is a specific instantiation of the general design theory nexus constructs. Using these illustrations, we provide examples of how to evaluate such instantiations. We then discuss our findings as well as the validity of our approach. We conclude that the design theory nexus provides a viable conceptualization that enables the construction of effective problem-solving artifacts.
Although increasing evidence suggests that superior performance requires alignment between firms' strategies and production processes, it is not known if such alignment is relevant for software development processes. This study breaks new ground by examining how firms align their software processes, products, and strategies in Internet application development. Drawing upon the literatures in strategy, operations management, and information systems, we identify four dimensions that influence alignment: the business unit strategy, the level of product customization, the level of process customization, and the volume of customers. To examine how these dimensions are synchronized, we conducted detailed case studies of Internet application development in nine varied firms including both start-ups and established "brick and mortar" companies. Our analyses reveal that the firms in our study do use differing processes for Internet application development, and that many of the firms match their software process choices to product characteristics, customer volume, and business unit strategies. We develop concept maps for the firms that are in alignment to illustrate how managers configure specific product and process dimensions. We also offer potential explanations for why some firms are misaligned, such as attempting to execute incompatible strategies, the lack of coordination between marketing and production strategies, the too rapid expansion of process scope, and inflexible barriers to rapid adaptation of process. Our study contributes detailed insights into how software processes and customized to complement different types of product requirements and strategies.